Voice-activated call pick-up for mobile device

ABSTRACT

Disclosed embodiments are directed an application program configured to run on a user&#39;s mobile device can allow voice-activated call pick-up to the user, without the user having to use his or her hands for picking up the call. For example, the application program can initially be trained to a user&#39;s voice command. When an incoming call is received at the mobile device, the user can pick up the call by issuing a voice command. In some embodiments, the application program can determine whether to allow voice-activated pick-up of calls based on data collected from multiple sensors associated with the vehicle, the mobile device, or a remote source.

BACKGROUND

Ubiquitous mobile communications devices, such as cellular phones,pagers, tablet devices, wearable devices, and personal digitalassistants (“PDAs”), have made it easier to reach a user regardless ofthe user's location. As long as the user has network connectivity, e.g.,via Wi-Fi, satellite, or cellular networks, he or she is able to receivecalls. But, there can be times when a user misses a call becauseinteracting with the mobile device is inconvenient or impossible. If auser is performing a task that requires both hands, or complete focus ofthe user, then the user may not be able to interact with the mobiledevice to pick up a call. For example, if a user is driving a vehiclewhen the mobile device rings, then it is unsafe for the user to pick upthe call.

Although there are currently some solutions that allow a user to use amobile device without having to physically hold the mobile device, thesesolutions still require the user to interact with the mobile device. Forexample, one solution provides a headset or a speakerphone function sothat the user driving a vehicle does not have to hold the mobile deviceduring a call. However, the user is still required to interact with themobile device to pick up the call and thereafter activate theheadset/speakerphone.

Another solution can be the use of a hands-free Bluetooth headset or anintegrated Bluetooth functionality included in the vehicle. But, evenwith these solutions, the user has to at least press one button to pickup the call. This can lead to unsafe driving, particularly when the useris driving in rocky terrain, crowded streets, bad weather, roads withpotholes, narrow lanes under construction, or any otherroad/environmental conditions that requires the undivided attention ofthe driver. Accordingly, there is a need for systems that allow driversto pick up calls while driving a vehicle without compromising theirsafety.

SUMMARY

A method for automated sensor-based communication using a mobile device,the method comprising: receiving first data from a first sensor;determining from the first data that the mobile device is located withina vehicle; receiving second data from a second sensor; determining fromthe second data that the vehicle is moving; receiving third data from athird sensor; determining from the third data an absence of interactionwith one or more physical inputs of the mobile device; receiving anindication of an incoming telephonic communication being received by themobile device; automatically activating a microphone operatively coupledto the mobile device; receiving one or more voice commands, the one ormore voice commands including a command to connect the incomingtelephonic communication; connecting the incoming telephoniccommunication via the microphone; receiving an indication that themobile device disconnected the incoming telephonic communication;determining from the third data a presence of interaction with the oneor more physical inputs of the mobile device; and disabling themicrophone operatively coupled to the mobile device.

It is to be understood that both the foregoing summary and the followingdetailed description are for purposes of example and explanation and donot necessarily limit the present disclosure. The accompanying drawings,which are incorporated in and constitute a part of the specification,illustrate subject matter of the disclosure. Together, the descriptionsand the drawings serve to explain the principles of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a representative environment of operation of someembodiments of the disclosed technology;

FIG. 2 illustrates an embodiment of the architecture of a mobile devicein accordance with some embodiments of the disclosed technology; and

FIG. 3 illustrates a process flow associated with voice-activated callpick-up for a mobile device.

DETAILED DESCRIPTION OF THE DRAWINGS

The following detailed description of the invention is merely exemplaryin nature and is not intended to limit the invention or the applicationand uses of the invention. Furthermore, there is no intention to bebound by any theory presented in the preceding background or thefollowing detailed description.

The various embodiments described herein provide apparatus, systems andmethods generally related to voice-activated call pick-up for a userdriving a vehicle. In some embodiments, an application programconfigured to run on a user's mobile device can allow voice-activatedcall pick-up to the user, without the user having to use his or herhands for picking up the call. For example, the application program caninitially be trained to a user's voice command. When an incoming call isreceived at the mobile device, the user can pick up the call by issuinga voice command. In some embodiments, the application program candetermine whether to allow voice-activated pick-up of calls based ondata collected from multiple sensors. For example, the method includesreceiving (e.g., from a first sensor) first data for determining thatthe mobile device and the user are located within a vehicle; receiving(from a second sensor) second data for determining that the vehicle ismoving; and receiving (from a third sensor) third data representing anabsence of interaction with one or more physical inputs of the mobiledevice. Upon receiving an indication of an incoming telephoniccommunication being received by the mobile device, the method includesactivating a microphone operatively coupled to the mobile device andreceiving one or more voice commands from the user to connect theincoming telephonic communication. Subsequently, after receiving anindication that the mobile device disconnected the incoming telephoniccommunication, the method includes determining from the third data apresence of interaction with the one or more physical inputs of themobile device and disabling the microphone operatively coupled to themobile device.

In some embodiments, the first data collected from a first sensor caninclude an indication that the mobile device is located within avehicle. Such an indication can be sent by the electronic circuitryinside the vehicle informing the mobile device over a short-rangewireless data connection (e.g., Bluetooth) that the mobile device isinside the vehicle. In some embodiments, such indication can be in theform of audible inputs (e.g., a user can select a “vehicle” mode in theapplication program) indicating that the mobile device is inside avehicle. In some embodiments, the first data from the first sensor caninclude the GPS coordinates received from the mobile device. The GPScoordinates received from the mobile device can be determined in avariety of ways. For example, the electronic circuitry inside thevehicle can provide the GPS coordinates of the vehicle to the mobiledevice. Accordingly, the application program can use the GPS coordinatesof the vehicle to estimate the location of the mobile device, based onthe mobile device being located within known GPS coordinate boundariesof the vehicle. As another example, the GPS coordinates of the mobiledevice may be based on processing one or more received wireless signals,e.g., WiFi/wireless triangulation from a WiFi hotspot or a geostationarysatellite in orbit.

In some embodiments, the second data collected from a second sensor caninclude an indication that the vehicle is moving. For example, a drivermay interact with one or more input devices (such as displays)operatively connected to the mobile device to confirm/select user asdriver of a vehicle. As another example, the application program canreceive information (from the circuitry inside the vehicle) over aBluetooth connection about the user getting inside the vehicle from asensor located in the driver-side door. As yet another example, theapplication program can receive information (from the circuitry insidethe vehicle) over a Bluetooth connection that the engine of the vehicleis running.

In some embodiments, the application program can determine theposition/location information of the mobile device with respect to thevehicle, e.g., if it is on the console, on the passenger seat, in thedriver's pocket, inside a bag/purse placed on the floor or a seat of thevehicle, etc. using proximity sensors coupled to the mobile device.

In some embodiments, the third data collected from a third sensor caninclude an indication of an absence of interaction with one or morephysical inputs of the mobile device. For example, the applicationprogram can receive information (from the circuitry inside the vehicle)over a Bluetooth connection receive information (from the circuitryinside the vehicle) indicating the absence of interaction with one ormore physical inputs of the mobile device. In some embodiments, theapplication program can self-sense a speed or an acceleration of themobile device by one or more sensors of the mobile device such as a GPSreceiver, an accelerometer, or a gyroscope. Further, the circuitryinside the vehicle can be any vehicle-related circuitry such as ignitioncircuitry, circuitry for operating windshield wipers, circuitry foroperating traction control, circuitry for operating lights of thevehicle, circuitry for operating air conditioner of the vehicle,circuitry for calculating a speed or an acceleration of the vehicle.Thus, according to disclosed embodiments, the third data can be one of:a geographical location of the vehicle, a road type associated with thevehicle, or a weather associated with the vehicle. Also, the thirdsensor may include at least one of: a GPS receiver, an accelerometer, ora gyroscope, a barometer, or a compass. The road type associated withthe vehicle may indicate whether the vehicle is on a congested road, anuncongested road, a highway, a city street, a pedestrian zone, ahospital, or a school zone. The third data can also include: a weatherevent or condition associated with the vehicle (e.g., snow on the road,as reported via Bluetooth, sensed by windshield wiper sensor, orreported by traction control).

In some embodiments, the disclosed application program matches theattributes set by the user with the first data, second data, third datacollected from the first sensor, the second sensor, and the third sensorrespectively. Upon detecting a successful match, the application programcauses an incoming call to be picked up by a voice command instead ofhaving to press any button on the mobile device. (In some cases, a usermay desire to have the voice-activated call pick-up functionality to bealways turned on, or never turned on. In such cases, no matching isnecessary.) A user may set any combination of attributes of speed anddriving location for the voice-activated call pickup to be operable. Forexample, a combination can be a vehicle speed of 55 mph and the drivinglocation being a highway. In another scenario, a user may set attributescorresponding to a vehicle speed of 10 mph and the driving locationbeing mountainous/hilly terrain. In some implementations, the user mayspecify road conditions as attributes for voice-activated call pick-up.Thus, a user may set the driving conditions as rocky or bumpy for thevoice-activated call pick-up functionality to operate. In anotherimplementation, a user may specify a weather type for thevoice-activated call pick-up functionality to operate. Thus, if theapplication program determines that the weather conditions where thevehicle is being driven correspond to a weather (e.g., rainy, stormy, orsnowy) set by the user, then the voice-activated call pick-up may beturned on.

FIG. 1 illustrates a representative environment of operation of someembodiments of the disclosed technology. In particular, FIG. 1 shows apartial view of a user driving a vehicle 102 and a mobile device 104communicating with one or more sensors located inside the vehicle oroutside the vehicle. For example, an application program running onmobile device 104 receives first data 110A from a first sensor locatedinside the vehicle, second data 1106 from a second sensor located insidethe vehicle, and third data 110C from a third sensor coupled to themobile device. It will be appreciated that the disclosed embodimentsimpose no restriction on the location of the sensors. That is, inalternate embodiments, sensors associated with the first data 110A, thesecond data 1106, or the third data 110C may be located in any one of:the mobile device 104, the vehicle 102, or associated with externalnetworks (e.g., a geostationary satellite 122 in orbit, and/or acellular tower 106). Examples of mobile device 104 can include a mobilephone, a tablet computer, a mobile media device, a mobile gaming device,or a wearable device such as a smartwatch. In FIG. 1, a sign 120 on theon the road where the vehicle is moving indicates the speed limit on theroad to be 60 mph.

In some embodiments, the first data 110A collected from a first sensorcan include an indication that the mobile device 104 is located withinvehicle 102. Such an indication can be sent by the electronic circuitryinside the vehicle 102 informing the mobile device 104 over a Bluetoothconnection that the mobile device 104 is inside the vehicle 102. In someembodiments, such indication can be in the form of physical/audibleinputs (e.g., a user can select a “vehicle” mode in the applicationprogram) indicating that the mobile device 104 is inside vehicle 102.

In some embodiments, the second data 110B collected from a second sensorcan include an indication that the vehicle 102 is moving. For example, adriver may interact with one or more input devices (such as displays)operatively connected to the mobile device 104 to confirm/select user asdriver of vehicle 102. As another example, the application program canreceive information (from the circuitry inside the vehicle 102) over aBluetooth connection about the user getting inside vehicle 102 from asensor located in the driver-side door. As yet another example, theapplication program can receive information (from the circuitry insidethe vehicle) over a Bluetooth connection that the engine of the vehicle102 is running. Another example can be the application program receivinginformation from a camera located on the vehicle indicating that thevehicle is moving. In some examples, the gyroscope or accelerometerlocated on the mobile device can determine that the vehicle is movingand convey that information to the application program.

In some embodiments, the third data 110C collected from a third sensorcan include an indication that the user is unable to interact with oneor more physical inputs of the mobile device 104. In some embodiments,the application program can self-sense a speed or an acceleration of themobile device 104 by one or more sensors of the mobile device 104 suchas a GPS receiver, an accelerometer, or a gyroscope. Further, thecircuitry inside the vehicle 102 can be any vehicle-related circuitrysuch as ignition circuitry, circuitry for operating windshield wipers,circuitry for operating traction control, circuitry for operating lightsof the vehicle, circuitry for operating air conditioner of the vehicle102, circuitry for calculating a speed or an acceleration of the vehicle102. Thus, according to disclosed embodiments, the third data 110C canbe one of: a speed of the vehicle 102, a geographical location of thevehicle 102, a road type associated with the vehicle 102, or a weatherassociated with the vehicle 102. Also, the third sensor may include atleast one of: a GPS receiver, an accelerometer, or a gyroscope, abarometer, or a compass. The road type associated with the vehicle 102may indicate whether the vehicle 102 is on a congested road, anuncongested road, a highway, a city street, a pedestrian zone, ahospital, or a school zone. The third data 110C can also include: aweather event or condition associated with the vehicle 102 (e.g., snowon the road, as reported via Bluetooth, sensed by windshield wipersensor, or reported by traction control).

When an incoming telephonic communication is received at mobile device104, the application program automatically activates a microphonecoupled to the mobile device 104. Then, the application program waitsfor a user to say one or more voice commands to connect to the incomingtelephonic communication. Upon identifying the voice command from theuser, the application program connects the incoming telephoniccommunication via the microphone of the mobile device 104. When the useror the caller hangs up the telephonic communication, the applicationprogram receives an indication from the mobile device that disconnectedthe telephonic communication. The application program then determinesfrom the third data 110C that there is a presence of interaction withthe one or more physical inputs of the mobile device. For example, theapplication program may receive a communication from the circuitryinside the vehicle 102 that the speed of the vehicle 102 is zero or lessthan 10 miles/hr, or that the ignition of the vehicle 102 is turned off.Then, the application program disables the microphone operativelycoupled to the mobile device 104, thereby turning off the functionalityfor receiving voice-activated calls.

Communications between mobile device 104 and tower 106 can be anycombination of local area and/or wide area networks, using wired and/orwireless communication systems. The networks could use any or moreprotocols/technologies: Ethernet, IEEE 802.11 or Wi-Fi, worldwideinteroperability for microwave access (WiMAX), cellulartelecommunication (e.g., 3G, 4G, 5G), CDMA, cable, digital subscriberline (DSL), etc. Similarly, the networking protocols may includemultiprotocol label switching (MPLS), transmission controlprotocol/Internet protocol (TCP/IP), User Datagram Protocol (UDP),hypertext transport protocol (HTTP), simple mail transfer protocol(SMTP), and file transfer protocol (FTP). Data exchanged over the one ormore networks may be represented using technologies, languages, and/orformats including hypertext markup language (HTML) or extensible markuplanguage (XML). In addition, all or some links can be encrypted usingconventional encryption technologies such as secure sockets layer (SSL),transport layer security (TLS), and Internet Protocol security (IPsec).Communications between mobile device 104 and satellite 122 can employsimilar technologies.

FIG. 2 illustrates an embodiment of the architecture of a mobile devicein accordance with some embodiments of the disclosed technology. FIG. 2illustrates a set of components within the mobile device according toone or more embodiments of the present disclosure. According to theembodiments shown in FIG. 2, the mobile device can include memory 205,one or more processors 210, sensor data collection module 215, thirdparty data module 225, microphone module 230, and microphone activationmodule 235. Other embodiments of the present invention may include some,all, or none of these modules and components, along with other modules,applications, and/or components. Still yet, some embodiments mayincorporate two or more of these modules and components into a singlemodule and/or associate a portion of the functionality of one or more ofthese modules with a different module.

Memory 205 can store instructions for running one or more applicationsor modules on processor(s) 210. For example, memory 205 could be used inone or more embodiments to house all or some of the instructions neededto execute the functionality of sensor data collection module 215, thirdparty data module 225, microphone module 230, and microphone activationmodule 235. Generally, memory 205 can include any device, mechanism, orpopulated data structure used for storing information. In accordancewith some embodiments of the present disclosure, memory 205 canencompass, but is not limited to, any type of volatile memory,nonvolatile memory, and dynamic memory. For example, memory 205 can berandom access memory, memory storage devices, optical memory devices,magnetic media, floppy disks, magnetic tapes, hard drives, SIMMs, SDRAM,DIMMs, RDRAM, DDR RAM, SODIMMS, EPROMs, EEPROMs, compact discs, DVDs,and/or the like. In accordance with some embodiments, memory 205 mayinclude one or more disk drives, flash drives, one or more databases,one or more tables, one or more files, local cache memories, processorcache memories, relational databases, flat databases, and/or the like.In addition, those of ordinary skill in the art will appreciate manyadditional devices and techniques for storing information that can beused as memory 205.

Sensor Data collection module 215 provides capabilities forreceiving/calculating the first data, the second data, and the thirddata respectively from the first sensor, the second sensor, and thethird sensor. The first data indicates that the mobile device is locatedwithin a vehicle. The second data indicates that the vehicle is moving.The third data indicates a lack or absence of interaction with one ormore physical inputs (e.g., keyboard, screen, etc.) of the mobiledevice. The first sensor, the second sensor, or the third sensor can belocated on the mobile device, the vehicle, or can be any other suitablesensor from which the mobile device can collect information. Accordingto disclosed embodiments, there are no restrictions on the type,location, or manufacturer of the first sensor, the second sensor, or thethird sensor.

Third party data module 225 can include data received from third partiesvia their application programming interfaces (APIs), applicationprograms, etc. For example, in some implementations, the disclosedapplication program can receive information from a third partypertaining to the weather. In some implementations, the disclosedapplication program can provide information to the user's vehicleinsurance provider informing the provider about the usage of thevoice-activated calling by the user. This information may be used by theprovider to assess the user's driving habits in lowering insurancepremiums. In some embodiments, the application program can receiveinformation (e.g., from proprietary or publicly-accessible geographicdatabases) about the road (e.g., a type of road and/or a location of theroad) on which the vehicle is moving.

Microphone module 230 allows the application program to receive theuser's voice communications during a call (e.g., from a microphonecoupled to the mobile device). The microphone module 230 includesanalog/digital circuitry and drivers for operation of the microphonecoupled to the mobile device.

Microphone activation module 235 allows the user to activate themicrophone to receive a voice command causing the incoming call to beanswered. The voice command can be a specific string of characters orwords that can be identified/recognized by the application program. Forexample, the application program can be trained to identify certainvoice commands for activating the microphone. The microphone may beactivated automatically by the incoming call and then may “listen” forthe voice commands.

FIG. 3 illustrates a process flow associated with voice-activated callpick-up of an incoming telephonic communication for a mobile device. Insome embodiments, steps associated with the process flow can beimplemented by an application program configured to run on a user'smobile device. At step 306, the process receives a first data from afirst sensor and determines (at step 308) from the first data that themobile device is located within a vehicle. At step 310, the processreceives second data from a second sensor and determines (at step 312)from the second data that the vehicle is moving. For example, a drivermay interact with one or more input devices (such as displays)operatively connected to the mobile device to confirm/select user asdriver of a vehicle. At step 314, the process receives third data from athird sensor and determines (at step 316) from the third data an absenceof interaction with one or more physical inputs of the mobile device.For example, the application program can receive information (from thecircuitry inside the vehicle) over a Bluetooth connection that the useris unable to interact with one or more physical inputs of the mobiledevice. The mobile device can be configured to run an operating systemand include additional programs with instructions for operating the oneor more physical inputs.

Examples of operating systems running on the user's mobile device can beMICROSOFT WINDOWS®, ANDROID®, or IOS®. Upon receiving information for anincoming call, the application program activates (at step 314) themicrophone coupled to the mobile device. The application programreceives an indication of an incoming telephonic communication at step318 and activates the microphone at step 320. At step 322, theapplication program detects whether a voice command was received (viathe microphone), e.g., within a predetermined time interval. In someimplementations, the predetermined time interval can be set by a user toa maximum number of rings that the application program will wait forreceiving a voice command (e.g., “pick up”) from the user. The voicecommand from the user can be a specific string of characters or wordsthat can be identified/recognized by the application program, after theuser has trained the application program to recognize the voice command.There is no restriction on the language or the number of words in thevoice command. Further, the voice command may not have any literalmeaning but can be used as a command by the user to instruct theapplication program to pick up an incoming call. Typically, theapplication program can undergo a prior training of recognizing thevoice command so that the application program is able toidentify/recognize the voice command and pick up the call. Theapplication program connects to the incoming telephonic communication atstep 324 via the microphone. The process receives (at step 326) anindication that the mobile device disconnected the incoming telephoniccommunication. At step 328, the process determines from the third datathat the user is able to interact with the mobile device. For example,the process determines that from a gyroscope coupled to the mobiledevice that the speed of the mobile device is zero or below a certainthreshold (e.g., 10 miles/hr). Alternatively, the process may receive amessage from the circuitry within the vehicle that the vehicle has cometo a standstill, and/or that the driver-side door is open. At step 330,the process disables the microphone on the mobile device.

In some scenarios, it is possible that the application program does notreceive the voice command from the user within the predetermined timeinterval or, the application program is not able to recognize the voicecommand (even if the voice command was received within the predeterminedtime interval). In such scenarios, the application program allows a userto manually pick up the call. If the application program detects thatthe user has not manually picked up the call within a certain timeinterval, the application program can divert the incoming call to avoicemail associated with the user.

Some of the embodiments described herein are described in the generalcontext of methods or processes, which may be implemented in oneembodiment by a computer program product, embodied in acomputer-readable medium, including computer-executable instructions,such as program code, executed by computers in networked environments. Acomputer-readable medium may include removable and non-removable storagedevices including, but not limited to, Read Only Memory (ROM), RandomAccess Memory (RAM), compact discs (CDs), digital versatile discs (DVD),etc. Therefore, the computer-readable media can include a non-transitorystorage media. Generally, program modules may include routines,programs, objects, components, data structures, etc. that performparticular tasks or implement particular abstract data types. Computer-or processor-executable instructions, associated data structures, andprogram modules represent examples of program code for executing stepsof the methods disclosed herein. The particular sequence of suchexecutable instructions or associated data structures representsexamples of corresponding acts for implementing the functions describedin such steps or processes.

Some of the disclosed embodiments can be implemented as devices ormodules using hardware circuits, software, or combinations thereof. Forexample, a hardware circuit implementation can include discrete analogand/or digital components that are, for example, integrated as part of aprinted circuit board. Alternatively, or additionally, the disclosedcomponents or modules can be implemented as an Application SpecificIntegrated Circuit (ASIC) and/or as a Field Programmable Gate Array(FPGA) device. Some implementations may additionally or alternativelyinclude a digital signal processor (DSP) that is a specializedmicroprocessor with an architecture optimized for the operational needsof digital signal processing associated with the disclosedfunctionalities of this application. Similarly, the various componentsor sub-components within each module may be implemented in software,hardware or firmware. The connectivity between the modules and/orcomponents within the modules may be provided using any one of theconnectivity methods and media that is known in the art, including, butnot limited to, communications over the Internet, wired, or wirelessnetworks using the appropriate protocols.

The foregoing description of embodiments has been presented for purposesof illustration and description. The foregoing description is notintended to be exhaustive or to limit embodiments of the presentinvention to the precise form disclosed, and modifications andvariations are possible in light of the above teachings or may beacquired from practice of various embodiments. The embodiments discussedherein were chosen and described in order to explain the principles andthe nature of various embodiments and its practical application toenable one skilled in the art to utilize the present invention invarious embodiments and with various modifications as are suited to theparticular use contemplated. The features of the embodiments describedherein may be combined in all possible combinations of methods,apparatus, modules, systems, and computer program products.

What is claimed is:
 1. A method for automated sensor-based communicationusing a mobile device, the method comprising: receiving first data froma first sensor; determining from the first data that the mobile deviceis located within a vehicle; receiving second data from a second sensor;determining from the second data that the vehicle is moving; receivingthird data from a third sensor; determining from the third data anabsence of interaction with one or more physical inputs of the mobiledevice; receiving an indication of an incoming telephonic communicationbeing received by the mobile device; automatically activating amicrophone operatively coupled to the mobile device; receiving one ormore voice commands, the one or more voice commands including a commandto connect the incoming telephonic communication; connecting theincoming telephonic communication via the microphone; receiving anindication that the mobile device disconnected the incoming telephoniccommunication; determining from the third data a presence of interactionwith the one or more physical inputs of the mobile device; and disablingthe microphone operatively coupled to the mobile device.
 2. The methodof claim 1, wherein the first data from the first sensor comprises:short-range wireless communication data connecting the vehicle with themobile device indicating that the mobile device is located within thevehicle or audible data indicating that the mobile device is locatedwithin the vehicle.
 3. The method of claim 2, wherein the first datafrom the first sensor comprises GPS coordinates received from the mobiledevice.
 4. The method of claim 3, wherein the GPS coordinates receivedfrom the mobile device are based on an estimated location of the mobiledevice within the vehicle.
 5. The method of claim 3, wherein the GPScoordinates received from the mobile device are based on processing oneor more received wireless signals.
 6. The method of claim 1, wherein thesecond data from the second sensor comprises: communication dataconnecting the vehicle with the mobile device indicating a speed of thevehicle or communication data connecting the vehicle with the mobiledevice indicating that the engine of the vehicle is running.
 7. Themethod of claim 1, wherein the third data from the third sensorcomprises: short-range wireless communication data connecting thevehicle with the mobile device indicating the absence of interactionwith the one or more physical inputs of the mobile device orself-sensing data received from the mobile device indicating the absenceof interaction with the one or more physical inputs of the mobiledevice.
 8. The method of claim 1, wherein the mobile device iselectronically coupled to at least one of: ignition circuitry of thevehicle, circuitry for operating windshield wipers of the vehicle,circuitry for operating traction control of the vehicle, circuitry foroperating lights of the vehicle, circuitry for operating air conditionerof the vehicle, or circuitry for calculating a speed or an accelerationof the vehicle.
 9. The method of claim 1, wherein the first sensor, thesecond sensor, or the third sensor are located on the mobile device andcomprises: a GPS receiver, an accelerometer, or a gyroscope, abarometer, or a compass.
 10. The method of claim 1, wherein the thirddata comprises: a geographical location of the vehicle, a road typeassociated with the vehicle, or a weather associated with the vehicle.11. The method of claim 1, wherein the command to connect the incomingtelephonic communication is received from the user within apredetermined time interval, further comprising: in an event of notreceiving the command to connect the incoming telephonic communicationwithin the predetermined time interval or not recognizing the command,the mobile device not connecting the incoming telephonic communication.12. The method of claim 11, wherein the mobile device not connecting theincoming telephonic communication comprises: allowing the user tomanually connect the incoming telephonic communication or diverting theincoming telephonic communication to voicemail.
 13. An electronic mobiledevice for automated sensor-based communication comprising: one or moreprocessors; and memory storing instructions thereon which cause the oneor more processors to: receive first data from a first sensor; determinefrom the first data that the mobile device is located within a vehicle;receive second data from a second sensor; determine from the second datathat the vehicle is moving; receive third data from a third sensor;determine from the third data an absence of interaction with one or morephysical inputs of the mobile device; receive an indication of anincoming telephonic communication being received by the mobile device;automatically activate a microphone operatively coupled to the mobiledevice; receive one or more voice commands, the one or more voicecommands including a command to connect the incoming telephoniccommunication; connect the incoming telephonic communication via themicrophone; receive an indication that the mobile device disconnectedthe incoming telephonic communication; determine from the third data apresence of interaction with the one or more physical inputs of themobile device; and disable the microphone operatively coupled to themobile device.
 14. The mobile device of claim 13, wherein the first datafrom the first sensor comprises: short-range wireless communication dataconnecting the vehicle with the mobile device indicating that the mobiledevice is located within the vehicle or audible data indicating that themobile device is located within the vehicle.
 15. The mobile device ofclaim 13, wherein the second data from the second sensor comprises:communication data connecting the vehicle with the mobile deviceindicating a speed of the vehicle or communication data connecting thevehicle with the mobile device indicating that the engine of the vehicleis running.
 16. The mobile device of claim 13, wherein the third datafrom the third sensor comprises: short-range wireless communication dataconnecting the vehicle with the mobile device indicating the absence ofinteraction with the one or more physical inputs of the mobile device orself-sensing data received from the mobile device indicating the absenceof interaction with the one or more physical inputs of the mobiledevice.
 17. A non-transitory computer-readable medium comprisinginstructions configured to cause at least one computer processor toperform a method comprising: receiving first data from a first sensor;determining from the first data that the mobile device is located withina vehicle; receiving second data from a second sensor; determining fromthe second data that the vehicle is moving; receiving third data from athird sensor; determining from the third data an absence of interactionwith one or more physical inputs of the mobile device; receiving anindication of an incoming telephonic communication being received by themobile device; automatically activating a microphone operatively coupledto the mobile device; receiving one or more voice commands, the one ormore voice commands including a command to connect the incomingtelephonic communication; connecting the incoming telephoniccommunication via the microphone; receiving an indication that themobile device disconnected the incoming telephonic communication;determining from the third data a presence of interaction with the oneor more physical inputs of the mobile device; and disabling themicrophone operatively coupled to the mobile device.
 18. Thenon-transitory computer-readable medium of claim 17, wherein the firstdata from the first sensor comprises: short-range wireless communicationdata connecting the vehicle with the mobile device indicating that themobile device is located within the vehicle or audible data indicatingthat the mobile device is located within the vehicle.
 19. Thenon-transitory computer-readable medium of claim 17, wherein the seconddata from the second sensor comprises: communication data connecting thevehicle with the mobile device indicating a speed of the vehicle orcommunication data connecting the vehicle with the mobile deviceindicating that the engine of the vehicle is running.
 20. Thenon-transitory computer-readable medium of claim 17, wherein the thirddata from the third sensor comprises: short-range wireless communicationdata connecting the vehicle with the mobile device indicating theabsence of interaction with the one or more physical inputs of themobile device or self-sensing data received from the mobile deviceindicating the absence of interaction with the one or more physicalinputs of the mobile device.